The latest updates on your projects. Learn more about Vercel for Git ↗︎

@dhruv-1001

Let's make this improvements in schema. Since, we don't have any relation of this table with other tables, we will directly migrate the data from old DB to new DB after making the transformations. This can be a low priority thing for now as there's no post processing that has to happen immediately.

1. camelCase table names make the queries syntactically harder when DB is directly queried through tools like Metabase. To be rethought if it's a good option.
2. Use DB Level Constraints. (e.g., if aadharVaultReference has a fixed length we can set it as constraint on DB as well). VARCHAR is preferred over text in this case. It is storage efficient
3. Should use the type specific field, like for DOB, it's good to use a date field as it makes querying easier as we get access to built in functions
4. Try to use ENUMs for field with fixed smaller number of values